Skip to content

Conversation

@n1v0lg
Copy link
Contributor

@n1v0lg n1v0lg commented Oct 21, 2024

There is a display glitch in the ES serverless API: see live spec.

where details of several APIs are rendered as API headers. This PR fixes the rendering issue by including the relevant header info in top-level comments for each affected API.

@github-actions
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
security.delete_role 🟢 8/8 8/8
security.get_builtin_privileges 🔴 2/2 1/2
security.get_role 🔴 24/24 21/24
security.put_role 🔴 31/39 38/38

You can validate these APIs yourself by using the make validate target.

@n1v0lg n1v0lg marked this pull request as ready for review October 21, 2024 12:00
Copy link
Contributor

@slobodanadamovic slobodanadamovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Nice catch!

import { Name, Refresh } from '@_types/common'

/**
* Delete roles API
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be an empty line between the header and the description.

The JSDoc is interpreted as markdown which means that no new paragraph is created without the empty line.

Same for all other places 🙂

Copy link
Contributor Author

@n1v0lg n1v0lg Oct 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@flobernd thanks!

Is this what you had in mind: 071eafe?

I don't think it affected the output directory so I don't think it'll make a difference in rendering though.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@n1v0lg Yes, the previous commit looks good! It should affect the ouput as well 😅 (maybe we have a bug here in the spec compiler, if it really does not..).

@github-actions
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
security.delete_role 🟢 8/8 8/8
security.get_builtin_privileges 🔴 2/2 1/2
security.get_role 🔴 24/24 21/24
security.put_role 🔴 31/39 38/38

You can validate these APIs yourself by using the make validate target.

1 similar comment
@github-actions
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
security.delete_role 🟢 8/8 8/8
security.get_builtin_privileges 🔴 2/2 1/2
security.get_role 🔴 24/24 21/24
security.put_role 🔴 31/39 38/38

You can validate these APIs yourself by using the make validate target.

@n1v0lg n1v0lg requested a review from flobernd October 21, 2024 12:34
@github-actions
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
security.delete_role 🟢 8/8 8/8
security.get_builtin_privileges 🔴 2/2 1/2
security.get_role 🔴 24/24 21/24
security.put_role 🔴 31/39 38/38

You can validate these APIs yourself by using the make validate target.

@github-actions
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
security.delete_role 🟢 8/8 8/8
security.get_builtin_privileges 🔴 2/2 1/2
security.get_role 🔴 24/24 21/24
security.put_role 🔴 31/39 38/38

You can validate these APIs yourself by using the make validate target.

Copy link
Member

@flobernd flobernd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you.

@n1v0lg n1v0lg merged commit 2fdec29 into main Oct 21, 2024
6 checks passed
@n1v0lg n1v0lg deleted the fix-role-mapping-related-api-spec branch October 21, 2024 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants